Method and Apparatus for Identifying and Using Radio Resources in a Wireless Communication Network

ABSTRACT

A network node, such as a base station, identifies radio resources within an overall bandwidth using a first resource referencing scheme, while a wireless communication device identifies radio resources within an allocated portion of the overall bandwidth using a second resource referencing scheme. Advantageously, the device correctly identifies given radio resources pointed to by a resource identifier expressed according to the first resource referencing scheme, by translating the resource identifier into the second resource referencing scheme according to mapping information that relates the two schemes. Correspondingly, the network node enables the wireless communication device to perform such translations by providing the mapping information either implicitly or explicitly.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/580,410 filed 7 Dec. 2017, which is a U.S. National Phase Applicationof PCT/SE2017/051081 filed 2 Nov. 2017, which claims benefit ofProvisional Application No. 62/417,565 filed 4 Nov. 2016. The entirecontents of each aforementioned application is incorporated herein byreference.

TECHNICAL FIELD

The present invention generally relates to wireless communicationnetworks, and particularly relates to identifying and using radioresources in such networks.

BACKGROUND

In wireless communication networks based on the Long Term Evolution(LTE) standards, it is known for a wireless communication device tooperate with a downlink bandwidth that matches the downlink bandwidthused by the supporting network base station, at least with respect to agiven downlink carrier. In this context, the Third GenerationPartnership Project (3GPP) refers to wireless communication devices as“User Equipments” or “UEs” and refers to base stations as “eNodeBs” or“eNBs.”

In LTE, a “resource block” or “RB” is the smallest unit of radioresources that can be allocated to a user and it “contains” a definednumber of Orthogonal Frequency Division Multiplex (OFDM) subcarriersover a defined interval. Thus, the overall bandwidth used on the DL maybe expressed in terms of the number of resource blocks spanned by thatbandwidth. Any particular set or sets of subcarriers within a giveninterval may be identified by identifying the corresponding RB number ornumbers. That is, the network may number the DL RBs starting with alowest number for the lowest frequency, or vice versa, and sequentiallynumber the RBs going up or down from that starting point. Of course,other numbering schemes may be used.

In a non-limiting example, bandwidth is measured in the number of RBs,where each RB corresponds to a fixed number of OFDM subcarriers. Thenumber could be one, two, twelve, twenty-six or any other number.Without loss of generality, one may assume that a base station in thewireless communication network counts or references its downlink radioresources in terms of RBs, e.g., starting with a low RB number for a lowfrequency and a higher RB number for a higher frequency. Of course, theopposite order may be used. In either case, a base station numbers theRBs comprising its overall downlink bandwidth using a numbering scheme,where each number identifies or points to a particular RB within thedownlink bandwidth.

In LTE, User Equipments (UEs) are configured to process the downlinkbandwidth used by their supporting eNBs, at least on a per-carrierbasis. Because the UE operates with the same bandwidth as the eNB, atleast with respect to individual carriers, the UE had the same “view” ofthe radio resources and the same resource numbering scheme could be usedin common between the eNB and the UE. Consequently, a resource pointertransmitted by the eNB using its numbering scheme can be received andinterpreted by the UE without ambiguity.

However, it is appreciated herein that resource identification becomesdecidedly more challenging to manage in new radio systems, also referredto as “5G” radio systems, which are being developed and deployed. Insuch radio systems, a given UE may support or be allocated only a subsetof the overall downlink bandwidth associated with a network basestation, and the location or position of the allocation within theoverall downlink bandwidth may vary. By way of example, see TS 38.801,Study on New Radio Access Technology.

As a further complication appreciated herein, in LTE, Physical DownlinkControl Channels (PDCCHs) are potentially transmitted over the entire(downlink) bandwidth, which requires individual UEs to monitor for PDCCHover the entire bandwidth. However, with new radio systems, there is awish to reduce the bandwidth of the PDCCH space. One bandwidth reductionapproach involves allocating a limited sub-band of the overall downlinkbandwidth for sending downlink control signaling (in one or a few OFDMsymbols).

This small allocation would represent a “common” PDCCH search space tobe monitored by all UEs supported by the base station. There may also bea need to configure UE-specific search spaces within the bandwidthallocations made for respective ones of the UEs. Such search spaces mayor may not overlap with the common search space, and it will beappreciated that UE-specific search spaces can be configured for each UEby assigning specific RBs within the UE's allocated bandwidth.

When sending a UE-specific message to a given UE, the base station couldexpress resource pointers or other resource identifiers using theresource numbering scheme of the UE. However, consider a PDCCH or othercontrol message that includes a resource pointer or other resourceidentifier and is intended for more than one UE, e.g., potentially manyUEs. The multiple UEs do not necessarily have the same configuredbandwidths or the same starting or reference locations for theirconfigured bandwidths within the overall downlink bandwidth. Hence,there is no numbering scheme commonly applicable to the base station andthe multiple UEs. Such control messages include, for example, randomaccess response messages, system information related messages, pagingmessages, broadcast service related messages (like MBMS) etc.

These control messages may contain a reference to a data region wheremore control content can be found, a pointer to the RBs where, forexample, the system info can be found. It is appreciated herein thatsuch a pointer or resource identifier expressed using the resourcenumbering scheme of the base station will be interpreted differently byUEs having different configured bandwidths or bandwidth positions withinthe overall downlink bandwidth.

To better appreciate the preceding problem, consider FIG. 1, where theoverall downlink bandwidth of interest includes RBs numbered from 0 to26 by the base station, (N−1)=26. A first UE, denoted as UE 1, operatesin an allocated subset of the overall downlink bandwidth and numbers RBswithin its allocated bandwidth using a numbering scheme going from 0 to(M1−1)=9. However, “0” within the numbering scheme used by the UE 1corresponds to “10” within the numbering scheme used by the basestation. Similarly, a second UE, denoted as UE 2, operates in anotherallocated subset of the overall downlink bandwidth and numbers RBswithin its allocated bandwidth using a numbering scheme going from 0 to(M2−1)=14. However, “0” within the numbering scheme used by the UE 2corresponds to “3” within the numbering scheme used by the base station.Note that M1 and M2 are less than or equal to N.

Now consider FIG. 2, which shows a common PDCCH message in RB 10. Ofcourse, it should be appreciated that a PDCCH might in practice spanseveral RBs and the format of the PDCCH message in this example contextis not important. What is important is that the PDCCH is intended formore than one UE and includes a resource identifier pointing to a dataregion (i.e., particular downlink resources) that the UEs should accessfor further content.

Assume that the data region is located in RBs 12-14 according to the BSnumbering. Those same RBs are, however, numbered as RBs 2-4 according tothe UE 1 numbering, and are numbered as RBs 9-11 according to the UE 2numbering. A tempting solution to these numbering differences is toforce all UEs to use the same numbering scheme as used by the basestation. As recognized herein, however, such an approach has amultiplicity of disadvantages. For example, identifying resources withina smaller number space requires fewer bits than are required foridentifying the same resources within a larger number space. Hence,forcing each UE to operate with the larger reference numbering space ofthe base station forfeits the opportunity to use more efficient resourceidentifiers for identifying UE-specific resources within the allocatedbandwidth associated with a given UE.

SUMMARY

A network node, such as a base station, identifies radio resourceswithin an overall bandwidth using a first resource referencing scheme,while a wireless communication device identifies radio resources withinan allocated portion of the overall bandwidth using a second resourcereferencing scheme. Advantageously, the device correctly identifiesgiven radio resources pointed to by a resource identifier expressedaccording to the first resource referencing scheme, by translating theresource identifier into the second resource referencing schemeaccording to mapping information that relates the two schemes.Correspondingly, the network node enables the wireless communicationdevice to perform such translations by providing the mapping informationeither implicitly or explicitly.

One example embodiment involves a method of operation in a wirelesscommunication device configured for operation in a wirelesscommunication network. The method includes receiving a resourceidentifier from a network node in the wireless communication network,and using the resource identifier to identify a corresponding radioresource within an allocated bandwidth of the wireless communicationdevice, if the resource identifier was received in a device-specificmessage. Alternatively, according to the method, the wirelesscommunication device translates the resource identifier and uses thetranslated resource identifier to identify the corresponding resourcewithin the allocated bandwidth of the user equipment, if the resourceidentifier was not received in a device-specific message. In eithercase, the method further includes the wireless communication devicetransmitting or receiving on the corresponding radio resource.

In the above context, resource identifiers not received indevice-specific messages comprise values expressed in a first resourcereferencing scheme that is referenced to an overall bandwidth andresource identifiers received in device-specific messages comprisevalues expressed in a second resource referencing scheme that isreferenced to the allocated bandwidth of the wireless communicationdevice. Correspondingly, translating resource identifiers expressedusing the first resource referencing scheme comprises using mappinginformation that relates the first resource referencing scheme to thesecond resource referencing scheme.

In a related example embodiment, a wireless communication deviceincludes communication circuitry configured for wireless communicationin a wireless communication network and processing circuitry operativelyassociated with the communication circuitry. The processing circuitry isconfigured to receive, via the communication circuitry, a resourceidentifier from a network node in the wireless communication network,and to use the resource identifier to identify a corresponding radioresource within an allocated bandwidth of the wireless communicationdevice, if the resource identifier was received in a device-specificmessage. However, if the resource identifier was not received in adevice specific message, the processing circuitry is configured totranslate the resource identifier and use the translated resourceidentifier to identify the corresponding resource within the allocatedbandwidth of the wireless communication device. Still further, theprocessing circuitry is configured to transmit or receive on thecorresponding radio resource, via the communication circuitry.

In the above context, resource identifiers not received indevice-specific messages comprise values expressed in a first resourcereferencing scheme that is referenced to an overall bandwidth, andresource identifiers received in device-specific messages comprisevalues expressed in a second resource referencing scheme that isreferenced to the allocated bandwidth of the wireless communicationdevice. Correspondingly, the processing circuitry is configured totranslate resource identifiers expressed using the first resourcereferencing scheme by using mapping information that relates the firstresource referencing scheme to the second resource referencing scheme.

Another example embodiment involves a method of operation in a networknode that is configured for operation in a wireless communicationnetwork. The method includes transmitting a resource identifier in amessage that is not specific to a wireless communication deviceoperating with an allocated bandwidth, where the resource identifieridentifies a radio resource to be used by the wireless communicationdevice and is expressed according to a first resource referencing schemethat is referenced to an overall bandwidth that contains the allocatedbandwidth. The method further includes providing mapping information tothe wireless communication device that enables the wirelesscommunication device to translate the resource identifier from the firstresource referencing scheme into a second resource referencing schemethat is used by the wireless communication device for referencing radioresources within the allocated bandwidth. The network node provides themapping information to the wireless communication device eitherexplicitly, e.g., via explicit signaling, or implicitly, e.g., based onallocating the allocated bandwidth at an offset or position within theoverall bandwidth that is associated with a corresponding mappingfunction known to the wireless communication device.

In a related example, a network node is configured for operation in awireless communication network and comprises communication circuitry andassociated processing circuitry. The processing circuitry is configuredto transmit a resource identifier in a message that is not specific to awireless communication device operating with an allocated bandwidth. Theresource identifier identifies a radio resource to be used by thewireless communication device and is expressed according to a firstresource referencing scheme that is referenced to an overall bandwidththat contains the allocated bandwidth.

The processing circuitry is further configured to provide mappinginformation to the wireless communication device that enables thewireless communication device to translate the resource identifier fromthe first resource referencing scheme into a second resource referencingscheme that is used by the wireless communication device for referencingradio resources within the allocated bandwidth. The processing circuitryprovides the mapping information either explicitly or implicitly. Forexample, as noted above, there may be an association between mappingfunctions and the positioning of the allocated bandwidth within theoverall bandwidth, such that the device knows the mapping function touse based on the offset or position of its allocated bandwidth.

Of course, the present invention is not limited to the above featuresand advantages. Those of ordinary skill in the art will recognizeadditional features and advantages upon reading the following detaileddescription, and upon viewing the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 are diagrams of example bandwidth allocations torespective wireless communication devices operating within an overalldownlink bandwidth associated with a network base station.

FIG. 3 is a block diagram of one embodiment of first and second nodesconfigured according to the teachings herein.

FIG. 4 is a logic flow diagram of one embodiment of processing at a UserEquipment (UE) according to the teachings herein.

FIG. 5 is a block diagram of one embodiment of a wireless communicationnetwork having a network node configured according to the network-sideteachings herein, and shown in context with a wireless communicationdevice configured according to the complementary device-side teachingsherein.

FIG. 6 is a block diagram of example circuitry details for the networknode and wireless communication device introduced in FIG. 5.

FIG. 7 is a logic flow diagram of one embodiment of a method ofprocessing at a network node.

FIG. 8 is a logic flow diagram of one embodiment of a method ofprocessing at a network node.

FIGS. 9-12 are diagrams of example bandwidth allocations to respectivewireless communication devices operating within an overall downlinkbandwidth associated with a network base station, and correspondingresource reference translation schemes.

DETAILED DESCRIPTION

FIG. 3 illustrates a first node 10 and a second node 12. The nodes 10and 12 are configured for operation in a wireless communication network,e.g., a cellular communications network. As a non-limiting example, thefirst node 10 comprises a network node operating within a wirelesscommunication network and the second node 12 comprises a wirelesscommunication device operating within the network. By way of example,the network node comprises a radio access node, such as a base stationof the network, and the second node 12 comprises a User Equipment (UE)or other wireless communication device configured for communicating withthe base station. However, the methods contemplated herein have broaderapplicability to various kinds of nodes and systems where differentnumbering or identification schemes may be used by different nodes, withrespect to at least some of the same communication resources.

In FIG. 3, a set 14 of radio resources 16 are associated with the firstnode 10. For example, the set 14 of radio resources 16 comprises a setof frequency resources, such as a set of subcarriers or resource blocks(RBs), each comprising one or more subcarriers. The set 14 of radioresources 16 may comprise the overall set of RBs defined for an OFDMcarrier. Regardless, the first node 10 uses a first resource referencingscheme for identifying resources 16 within the overall set 14, alsoreferred to as an “overall bandwidth”. For example, the first node 10uses numbers within a first number space large enough to uniquelyidentify all resources 16 within the set 14.

The second node 12 is allocated or otherwise associated with a subset 18of the resources 16, and it uses a second resource referencing schemefor identifying resources 16 within the subset 18, also referred to asan “allocated bandwidth”. To the extent that the subset 18 does notencompass the full set 14 of resources 16, the second node 12 may use asmaller number space or more compact referencing scheme, which has theadvantage of requiring fewer bits to identify resources 16 within thesubset 18, but which has the disadvantage of diverging from thereferencing scheme used by the first node 10.

However, the first and second nodes 10 and 12 are configured to obviatethe issues arising from using different resource referencing schemes,where such configuration enables the second node 12 to accuratelyidentify a radio resource 16 within its subset 18 of resources 16, evenwhen the resource is identified by the first node 10 using the firstresource referencing scheme. In one example of such reconciliation ofthe two schemes, a method of operation by the second node 12 includesreceiving a first resource identifier from the first node 10, where thefirst resource identifier is expressed using the first resourcereferencing scheme. While the first resource identifier identifies aradio resource that falls within the subset 18, the first resourceidentifier points to or otherwise identifies the radio resource using avalue referenced to resource identification within the full set 14.Therefore, the second node 12 translates the first resource identifierinto a second resource identifier—also referred to as a “translated”resource identifier using mapping information that relates the firstresource referencing scheme to the second resource referencing scheme.The translated resource identifier points to the same radio resourcepointed to by the first resource identifier, but its value is expressedin terms of the second resource referencing scheme. The method furtherincludes transmitting or receiving on the corresponding radio resource,i.e., the radio resource identified by the translated resourceidentifier. (Here, it will be appreciated that the transmitting orreceiving via the resource involves one or more defined transmissiontime intervals or instants, e.g., slots, subframes, depending on thedetails of the air interface.)

The method may further include the second node 12 receiving a resourceidentifier from the first node 10 that is expressed in terms of thesecond resource referencing scheme. Thus, no translation is required andthe second node 12 uses the resource identifier without translation, toidentify the corresponding radio resource within the allocated subset18. Again, the second node 12 transmits or receives on the correspondingradio resource. In other words, for resource identifiers expressed inthe second resource referencing scheme, the second node 12 does notapply the mapping function—i.e., does not perform translation—andinstead uses them directly.

Thus, the second node 12 may be understood as selectively translatingreceived resource identifiers. For example, the first node 10 may fromtime to time send messages that are not specifically targeted to thesecond node 12, e.g., they may be targeted to multiple such nodes, eachhaving a respectively allocated subset 18. In such messages, the firstnode 10 expresses any included resource identifiers using the firstresource referencing scheme which is “common” or “global” to the overallor full set 14 of resources 16. Further, the first node 10 may from timeto time send messages that are specifically targeted to the second node12, and any resource identifiers included in such messages may beexpressed using the second resource referencing scheme in use by thesecond node 12. Put another way, when sending resource identifiers thathave to be interpreted by multiple nodes, with each such node having apotentially different allocated subset 18 of resources 16 and using acorrespondingly tailored resource referencing scheme, the node 10 usesthe first resource referencing scheme to express resource identifiersand relies on the respective receiving nodes to perform the neededtranslations. When sending resource identifiers targeted to a specificnode, however, the node 10 may use the particular resource referencingscheme applicable to that specific node.

FIG. 4 illustrates a method 400 according to preceding example. Themethod 400 is performed by a User Equipment (UE) or other wirelesscommunication device operating in a wireless communication network andincludes receiving (block 402) a resource identifier from a network nodein the wireless communication network. The method 400 continues withusing (block 406) the resource identifier to identify a correspondingradio resource within an allocated bandwidth of the wirelesscommunication device, if the resource identifier was received in adevice-specific message (yes from block 404). However, if the resourceidentifier was not received in a device specific message (no from block404), the method includes performing the operations of block 408 ratherthan block 406; namely, the wireless communication device translates theresource identifier and uses the translated resource identifier toidentify the corresponding resource within the allocated bandwidth ofthe wireless communication device. In either case, the resourceidentifier or translated resource identifier identify the samecorresponding radio resource and the method 400 further includestransmitting or receiving on the corresponding radio resource (block410).

In the context of the method 400, resource identifiers not received indevice-specific messages comprise values expressed in a first resourcereferencing scheme that is referenced to an overall bandwidth—e.g., thefull set 14 of resources 16—and resource identifiers received indevice-specific messages comprise values expressed in a second resourcereferencing scheme that is referenced to the allocated bandwidth of thewireless communication device—e.g., the allocated subset 18 of resources16. Thus, translating resource identifiers expressed using the firstresource referencing scheme comprises the wireless communication deviceusing mapping information that relates the first resource referencingscheme to the second resource referencing scheme.

In at least some embodiments, the resource identifier received by thewireless communication device references, as said corresponding radioresource, a radio resource region or a set of radio resources accordingto the first resource referencing scheme. Correspondingly, thetranslated resource identifier references the radio resource region orthe set of radio resources according to the second resource referencingscheme.

In one example, the first resource referencing scheme comprises a firstnumbering space used for numbering radio resources within the overallbandwidth, and the second resource referencing scheme comprises a secondnumbering space used for numbering radio resources within the allocatedbandwidth. Correspondingly, the wireless communication device translatesa resource identifier from the first resource referencing scheme to thesecond resource referencing scheme by translating from the firstnumbering space into the second numbering space according to a definedmapping function. Here, the defined mapping function constitutes themapping information mentioned above and relates numbers from the firstnumbering space to corresponding numbers from the second numberingspace.

Receiving the resource identifier at the wireless communication devicecomprises, for example, receiving a downlink control message transmittedby a base station in the wireless communication network on radioresources within a common search space used for sending downlink controlmessages to multiple wireless communication devices. Correspondingly,the wireless communication device determines that the resourceidentifier was not received in a device-specific message and, therefore,requires translation.

The wireless communication device may receive the mapping informationfrom the network. For example, the wireless communication devicereceives the mapping information via explicit signaling sent from thenetwork to the wireless communication device. Alternatively, the networkmay provide the mapping information to the wireless communication deviceimplicitly. For example, in one or more embodiments, the position oroffset of the allocated bandwidth within the overall bandwidth indicatesthe mapping function that the wireless communication device should usefor translating resource identifiers from the first resource referencingscheme into the second resource referencing scheme. In such embodiments,a node in the wireless communication network can provide the mappinginformation to the wireless communication device implicitly, by sendingconfiguration information defining the allocated bandwidth.

Thus, in one or more embodiments, the wireless communication devicereceives the mapping information in conjunction with receivingconfiguration information defining the allocated bandwidth, where thebandwidth allocation implicitly indicates the mapping or where theconfiguration information includes an explicit indication of themapping. In other embodiments, the mapping information comes separatelyfrom the bandwidth allocation.

In any case, in at least some embodiments, the corresponding radioresource identified by a resource identifier received by the wirelesscommunication device belongs to a set of radio resources pointed to bythe resource identifier. The set of radio resources carry data orcontrol information, and the wireless communication device uses theresource identifier, or the corresponding translated resourceidentifier, to identify the set of radio resources. Once the set ofradio resources is identified, the wireless communication device decodesthe data or control information conveyed on them. Alternatively, thewireless communication device uses the identified radio resources forone or more transmissions by the device.

FIG. 5 illustrates one embodiment of a wireless communication network 20(“network 20”) that provides one or more communication services to awireless communication device 22 (“WCD 22” or “device 22”), such as bycommunicatively coupling the device 22 to one or more external networks24. Example external networks 24 include the Internet or other PacketData Networks (PDNs). The network 20 includes a Radio Access Network(RAN) 26 including one or more network nodes 28, which may be referredto as base stations, access points, etc. A Core Network (CN) 30provides, e.g., mobility management and packet routing for the device22, and includes one or more CN nodes 32, such as packet gateways,mobility management entities, authentication servers, etc.

The diagram shall be understood as being simplified, as the network 20may include multiple other nodes of the same or different types, and mayinclude multiple base stations 28 and may include more than one RAN andmay operate with more than one Radio Access Technology (RAT). In oneexample, different types of base stations 28 provide a heterogenousradio access network, which may involve more than one RAT. Further, inthe context of 5G implementations, the network 20 may use beamforming,e.g., wherein allocated beams within a potentially large plurality ofbeams from one or more base stations 28 are used to provide coverage tothe device 22.

Still further, unless otherwise noted, the terms “device,” “wirelesscommunication device,” “user equipment,” and “UE” are usedinterchangeably herein. Unless otherwise specified, a wirelesscommunication device comprises essentially any apparatus configured forwirelessly connecting to the network 20 via any one or more of the RadioAccess Technologies (RATs) used by the network 20. A wirelesscommunication device may be mobile, although fixed devices are alsocontemplated, and non-limiting examples include cellularradiotelephones, which may be smartphones or feature phones, laptops,tablets, wireless modems or adaptors, Machine-to-Machine (M2M) orMachine-Type-Communication (MTC) devices, Internet-of-Things (IoT)devices, etc.

FIG. 6 illustrates example implementations of the base station 28 andthe device 22. In at least one example case, the base station 28 can beunderstood as an example of the node 10 illustrated in FIG. 3 and thedevice 22 can be understood as an example of the node 12 in the sameillustration.

The device 22 includes communication circuitry 40 that is configured forwireless communication in the network 20. In an example embodiment, thecommunication circuitry 40 comprises or includes RF transceivercircuitry 42 configured for radio communications in accordance with oneor more applicable air interface protocols.

The device 22 further includes processing circuitry 46 that isoperatively associated with the communication circuitry 40. Theprocessing circuitry 46 is configured to receive, via the communicationcircuitry 40, a resource identifier from a network node in the network20, e.g., to receive the resource identifier via a downlink transmissionby a base station 28 in the network 20. If the resource identifier wasreceived in a device-specific message, the processing circuitry 46 isconfigured to use the resource identifier to identify a correspondingradio resource within an allocated bandwidth 18. However, if theresource identifier was not received in a device-specific message, theprocessing circuitry 46 is configured to translate the resourceidentifier and use the translated resource identifier to identify thecorresponding resource within the allocated bandwidth 18 of the device22.

In either case, the resource identifier or the translated resourceidentifier identify the same corresponding radio resource, and theprocessing circuitry is configured to transmit or receive on thecorresponding radio resource, via the communication circuitry 40.Whether the device 22 transmits or receives on the corresponding radioresource depends, for example, on the type of message in which theresource identifier is received, or on the context in which the resourceidentifier is received.

Resource identifiers not received in device-specific messages comprisevalues expressed in a first resource referencing scheme that isreferenced to an overall bandwidth 14 and resource identifiers receivedin device-specific messages comprise values expressed in a secondresource referencing scheme that is referenced to the allocatedbandwidth 18 of the device 22. Correspondingly, the processing circuitry46 is configured to translate resource identifiers expressed using thefirst resource referencing scheme by using mapping information thatrelates the first resource referencing scheme to the second resourcereferencing scheme.

In an example embodiment, or an example case, the processing circuitry46 is configured to receive the resource identifier in a downlinkcontrol message transmitted by the base station 28 on radio resourceswithin a common search space used for sending downlink control messagesto multiple wireless communication devices (which may be of the same ordifferent types), and correspondingly determine that the resourceidentifier was not received in a device-specific message and, therefore,requires translation.

In at least one example embodiment or case, the processing circuitry 46is configured to receive the mapping information from the network 20,for translating resource identifiers from the first resource referencingscheme into the second resource referencing scheme. For example, theprocessing circuitry 46 is configured to receive the mapping informationin conjunction with receiving configuration information defining theallocated bandwidth. The processing circuitry 46 is configured to, forexample, receive the mapping information implicitly via a command sentby the network 20 to configure the allocated bandwidth 18. Here, aposition or offset of the allocated bandwidth 18 in the overallbandwidth 14 indicates a mapping function to be used by the device 22for translating resource identifiers from the first resource referencingscheme to the second resource referencing scheme.

In a further example, the radio resource corresponding to the receivedresource identifier belongs to a set of radio resources pointed to bythe resource identifier. The set of radio resources carry data orcontrol information, and the processing circuitry 46 is configured todecode the data or control information from the set of radio resources.For example, the base station 28 sends a downlink control message thattargets a plurality of devices, including the device 22, and theresource identifier identifies a set of radio resources within theoverall bandwidth 14. The identified resources commonly fall within therespective allocated bandwidths 18 of the targeted plurality of devices.

The communication circuitry 40 of the device 22 may also supportDevice-to-Device (D2D) communications directly with other devices 22,and may include WLAN communications, Bluetooth communications,Near-Field Communication (NFC), etc. Further, the processing circuitry46 comprises fixed circuitry, or programmed circuitry, or a mix of fixedand programmed circuitry.

In at least one embodiment, the processing circuitry 46 comprises one ormore microprocessors, Digital Signal Processors (DSPs), FieldProgrammable Gate Arrays (FPGAs), Application Specific IntegratedCircuits (ASICS), or other digital processing circuitry. In at least onesuch embodiment, the processing circuitry 46 is configured according tothe teachings herein based on the execution of computer programinstructions stored in one or more computer programs 50 held in storage48 that is included in or associated with the processing circuitry 46.The storage 48 may further hold one or more items of configuration data52 that is pre-provisioned and/or dynamically acquired by the processingcircuitry 46.

In one or more embodiments, the storage 48 comprises one or more typesof computer-readable media, such as a mix of non-volatile memorycircuits or disk storage and volatile, working memory. Non-limitingexamples of non-volatile storage include Solid State Disk (SSD) storage,FLASH, and EEPROM, while non-limiting examples of the volatile, workingmemory includes DRAM or SRAM.

FIG. 6 also illustrates example implementation details for the basestation 28, as an example of the network node 10 introduced in FIG. 3.The base station 28—and, more generally, the network node 10—includescommunication circuitry 60. The particular circuitry included in thecommunication circuitry 60 depends upon the type of network nodeinvolved.

In the illustrated example, the communication circuitry 60 includes RFtransceiver circuitry 62 and network node (“NW”) interface circuitry 64.The RF transceiver circuitry 62 includes physical-layer circuitry fortransmitting and receiving wireless signals, e.g., over the applicableair interface supporting communication with wireless devices operatingin the network. The network node interface circuitry 64 comprises, forexample, network interface circuitry for communicatively coupling thebase station 28 to one or more other base stations and/or other nodes inthe network 20.

The base station 28 further includes processing circuitry 66 that isoperatively associated with the communication circuitry 60. Theprocessing circuitry 66 is configured to transmit a resource identifierin a message that is not specific to a wireless communication device 22operating with an allocated bandwidth 18. For example, the base station28 transmits a message intended for a plurality of devices, rather thanbeing targeted to a specific device. While “transmit” in this contextcomprises wireless transmission via the communication circuitry 60, inother embodiments a network node 10 may transmit the resource identifierover a computer network link or other an inter-node interface, forwireless transmission.

In either case, the resource identifier identifies a radio resource tobe used by the wireless communication device, where the resourceidentifier is expressed according to a first resource referencing schemethat is referenced to an overall bandwidth 14 that contains theallocated bandwidth 18 of the device 22. Correspondingly, the processingcircuitry 66 is configured to provide mapping information to the device22. The mapping information enables the device 22 to translate theresource identifier from the first resource referencing scheme into asecond resource referencing scheme that is used by the device 22 forreferencing radio resources within the allocated bandwidth 18. Forexample, the processing circuitry 66 is configured to provide themapping information by explicitly signaling the mapping information tothe device 22, via the communication circuitry. Non-limiting examples ofexplicit signaling include sending one of: Radio Resource Control (RRC)signaling, a Medium Access Control (MAC) element, and control-channelsignaling.

In one or more other embodiments or instances, the processing circuitry66 is configured to provide the mapping information to the device 22implicitly, based on allocating the allocated bandwidth at an offset orposition within the overall bandwidth. The offset or position isassociated with a corresponding mapping function known to the wirelesscommunication device, for mapping from the first resource referencingscheme into the second resource referencing scheme.

In one example of transmitting a resource identifier in a message thatis not specific to the device 22, the processing circuitry 66 isconfigured to transmit a control channel within a common search spacethat is searched by a plurality of wireless communication devices fordownlink control information. Here, the plurality of wirelesscommunication devices includes the device 22 and the control channelconveys or otherwise indicates the resource identifier.

In this context, it shall be understood that the device 22 is configuredto translate resource identifiers received in messages that are notspecific to the device 22 and identify the corresponding radio resourceswithin the allocated bandwidth 18 using the translated resourceidentifiers. Conversely, the device 22 is configured to use, withouttranslation, resource identifiers received in messages that are specificto the device 22. The processing circuitry 66 of the network node10/base station 28 is, in at least some embodiments, configured toenable the device 22 to differentiate between device-specific andnon-device-specific messages by using a compact message format fortransmitting device-specific messages to the device 22, as compared to amessage format used for transmitting non-device-specific messages.

In at least some embodiments, the first resource referencing schemecomprises a first numbering scheme for numbering radio resources withinthe overall bandwidth, and the second resource referencing schemecomprises a second numbering scheme for numbering radio resources withinthe allocated bandwidth. The mapping information, therefore, enables thedevice 22 to translate numbers in the first numbering scheme intocorresponding numbers in the second numbering scheme. In these and inother embodiments, the processing circuitry 66 may be configured todetermine the mapping information in dependence on where the allocatedbandwidth 18 is positioned or located within the overall bandwidth 14.

The processing circuitry 66 comprises programmed circuitry, fixedcircuitry, or some combination of programmed and fixed circuitry. In anexample implementation, the processing circuitry includes one or moremicroprocessor-based circuits or other digital processing circuitry thatis specially adapted or otherwise configured based on the execution ofcomputer program instructions contained in one or more computerprograms. In a corresponding implementation example, the processingcircuitry 66 includes or is associated with storage 68 comprising one ormore types of computer-readable media that store the one or morecomputer programs 70 along with any applicable configuration data 72.

FIG. 7 illustrates a method 700 of operation performed by a network node10, such as the base station 28. For this method and other methodsillustrated herein, the method may be carried out in an order differentthan that suggested by the illustration. Further, it will be appreciatedthat the disclosed method(s) may be repeated on a triggered or as-neededbasis, e.g., when a device 22 initially connects to a network 20, when adevice 22 is handed over from one base station 28 to another, orwhenever the bandwidth allocation 18 of a device 22 is changed for anyreason.

The method 700 includes transmitting (block 702) a resource identifierin a message that is not specific to a wireless communication device 22operating with an allocated bandwidth 18, where the resource identifieridentifies a radio resource to be used by the device 22 and is expressedaccording to a first resource referencing scheme that is referenced toan overall bandwidth 14 that contains the allocated bandwidth 18. Themethod 700 further includes providing (block 704) mapping information tothe device 22 that enables the device 22 to translate the resourceidentifier from the first resource referencing scheme into a secondresource referencing scheme that is used by the device 22 forreferencing radio resources within the allocated bandwidth 18.

Providing the mapping information comprises, for example, explicitlysignaling the mapping information to the device. Examples of explicitsignaling include sending RRC signaling, sending MAC element, andsending control-channel signaling. Alternatively, the method 700includes providing the mapping information implicitly. For example,providing the mapping information implicitly comprises allocating theallocated bandwidth 18 at an offset or position within the overallbandwidth 14 that is associated with a corresponding mapping functionknown to the device 22, for mapping from the first resource referencingscheme into the second resource referencing scheme. Thus, indicating theallocated bandwidth 18 implicitly indicates the mapping function to beused by the device 22.

In an example of transmitting a resource identifier in the message thatis not specific to a particular device, the base station 28 or othernetwork node 10 in question transmits a control channel within a commonsearch space that is searched by a plurality of devices for downlinkcontrol information. The plurality of devices includes the device 22 inquestion and the involved search space occupies a portion of the overallbandwidth 14 that is common to the respective allocated bandwidths 18 ofthe involved devices.

Supporting such network-side operations, the device 22 is configured totranslate resource identifiers received in messages that are notspecific to the device 22 and identify the corresponding radio resourceswithin the allocated bandwidth 18 using the translated resourceidentifiers. However, the device 22 uses, without translation, resourceidentifiers received in messages that are specific to the device 22.Thus, in at least one embodiment, the method 700 includes enabling thedevice 22 to differentiate between device-specific andnon-device-specific messages by using a compact message format fortransmitting device-specific messages to the device 22 within adevice-specific search space in the allocated bandwidth 18, as comparedto a message format used for transmitting non-device-specific messagesin a common search space within the allocated bandwidth 18.

Notably, the method 700 may further include, and a network node 10/basestation 28 may be further configured to selectively send resourceidentifiers using a first resource referencing scheme relating to anoverall bandwidth 14 or a second resource referencing scheme relating toan allocated bandwidth 18 within the overall bandwidth 14. For example,when sending a resource identifier that has applicability to more thanone device operating in the network 20, the network node 10/base station28 sends the resource identifier as expressed in the first resourcereferencing scheme. Doing so allows each receiving device to translatethe resource identifier, as needed, into the particular referencingscheme in use at the device—e.g., different devices have differentallocated bandwidths 18, such that the different devices perform adifferent translation of the resource identifier so that thecorresponding radio resource is correctly identified within theirrespective allocated bandwidths 18. This approach saves the network 20from having to tailor the transmission to the particular bandwidthallocations of the receiving devices.

On the other hand, when sending a resource identifier that is targetedto one specific device 22, the network node 10/base station 28 sends theresource identifier as expressed in the resource referencing schemeapplicable to the device 22. Doing so promotes efficiency. For example,resource identifiers expressed in the resource reference applicable tothe targeted device 22 may be smaller than resource referenceidentifiers applicable to the overall bandwidth 14. Further, sending theresource identifier expressed in the referencing scheme in use at thetargeted device 22 avoids the targeted device 22 from having to performthe translation.

FIG. 8 illustrates a method 800 operation in a base station 28, such asin the base station 28 shown in FIG. 6. The method 800 can be understoodas a detailed example or extension of the method 700.

The method 800 includes signaling (Block 802) a downlink bandwidthallocation to a device 22 being served by, or to be served by, the basestation 28. The downlink bandwidth allocation indicates a seconddownlink bandwidth to be associated with the device 22, where the seconddownlink bandwidth is contained within a first downlink bandwidth thatis associated with the base station 28. Here, the first downlinkbandwidth corresponds to the earlier described overall bandwidth 14 andthe second downlink bandwidth corresponds to the earlier describedallocated bandwidth 18.

The method 800 further includes transmitting (Block 804) a downlinkmessage for reception by a plurality of devices 22, including theaforementioned device 22. The downlink message includes a resourceidentifier that identifies a radio resource containing data or controlinformation for the plurality of devices 22. The radio resourceidentifier has a value defined by a first resource referencing schemeused by the base station 28 for identifying radio resources within thefirst downlink bandwidth, and the method 800 further includes providing(Block 806), either explicitly or implicitly, mapping information to thedevice 22 that enables the device 22 to translate the resourceidentifier from the first resource referencing scheme into a secondresource referencing scheme used by the device 22 for referencing radioresources within the second downlink bandwidth.

With the above non-limiting examples in mind, in at least oneembodiment, a network node 10 transmits a device-specific offset to adevice 22 operating in a network 20. By way of example, thedevice-specific offset is transmitted via RRC messaging, as a MACelement, in control signaling, or by another mechanism. However conveyedfrom the network 20 to the device 22, the device-specific offset can beunderstood as providing or relating to mapping information that relatesthe resource numbering or referencing schemed used by the device 22 forreferencing radio resources within an allocated bandwidth 18, to theresource numbering or referencing scheme used by the network 20 forreferencing radio resources within an overall bandwidth 14 that containsthe allocated bandwidth 18.

Here, it will be understood that the term “bandwidth” as a matter ofconvenience is being used to connote both the amount or span andlocation of frequency resources. Thus, saying that a base station 28 isassociated with a downlink bandwidth of 100 MHz, for example, can beunderstood as saying that the base station is associated with 100 MHz ofradio frequency spectrum in a particular range of absolute frequency.Correspondingly, a device 22 operating in the coverage area of the basestation operates in a particular sub-band of the base station'sfrequency band, which sub-band is referred to as the allocated bandwidth18 associated with the device. In general, a particular bandwidth may bedefined by or contain a corresponding number of subcarriers having adefined spacing and each representing a frequency resource within thebandwidth.

In one or more embodiments, the network 20 transmits the device-specificoffset to a given device 22 whenever needed, e.g., whenever thebandwidth allocation of the device 22 changes or the mapping mustotherwise be updated. Preferably, the device-specific offset istransmitted in the same message used to configure the location of thedevice's allocated bandwidth 18. However, it is also contemplated hereinthat the device-specific offset can be signaled to a device 22 on animplicit basis. For example, based on known relationships, the device 22may derive the device-specific offset from the command that(re)allocates the device's bandwidth 18 within the overall bandwidth 14,which may be the system carrier bandwidth of the base station 28providing the involved downlink carrier.

As noted, allowing the devices to operate with device-specific resourcereferencing schemes allows device-specific resource identifiers to beexpressed in the “smaller” number spaces associated with the typicallymuch smaller bandwidth allocations associated with the respectivedevices 22. Note that the device-specific offset for a given device 22can be calculated by the network 20 in relation to any desired referencepoint within (or even outside) the system carrier bandwidth. Forexample, the offset may be calculated with respect to thelowest-numbered Resource Block (RB) within the system carrier bandwidth,or with respect to the center of the bandwidth, or with respect to thehighest-numbered RB. As a further alternative, the device-specificoffset may be referenced to the frequency location of a particularsignal (e.g., a synchronization signal or synchronization signal blockSSB or Physical Broadcast Channel, PBCH), or may be referenced to afrequency used by the device 22 for random access, or referenced to thelocation of the signaling used to convey the device-specific offset tothe device 22. As a further alternative, the device-specific offset canbe calculated to any arbitrary frequency, RB, or defined signal.

FIG. 9, for example, shows an approach where a base station (BS) 28 orother network node 10 uses a first resource referencing scheme toidentify radio resources within a set of radio resources. Specifically,the base station 28 uses a first numbering scheme that identifies 27 RBsusing the numbers 0 to 26. The 27 RBs represent an overall bandwidth forpurposes of this example, and a first device 22, denoted as UE1, isallocated a subset of that bandwidth encompassing RBs 10-19 (accordingto the BS numbering). Similarly, a second device 22, denoted as UE 2, isallocated another subset of the overall bandwidth, encompassing RBs 3-17(according to the BS numbering). Each UE uses its own resourcereferencing scheme, e.g., the UE 1 identifies the resources within itsallocated bandwidth using a numbering scheme going from 0 to 9, whilethe UE 2 identifies the resources within its allocated bandwidth using anumbering scheme going from 0 to 14.

Thus, relative to the “start” of the BS numbering scheme, the numberingscheme used by the UE 1 is offset by 10, and the numbering scheme usedby the UE 2 is offset by 3. The base station 28 can, therefore, provideeach of the UEs with a mechanism for translating from the base stationnumbering scheme into the numbering scheme used by the UE, by providingthe UE with the applicable offset information. Such information isprovided, for example, as part of configuring the bandwidth allocationfor the UE and may be signaled to the UE along with relatedconfiguration signaling.

Here, the UE-specific offsets can be understood as UE-specific mappinginformation that enables a given UE to translate a resource identifierfrom a first resource referencing scheme used by the base station 28 foridentifying radio resources within a first downlink bandwidth associatedwith the base station 28 into a second resource referencing scheme usedby the UE for identifying radio resources within a second downlinkbandwidth associated with the UE. In this example, the first downlinkbandwidth comprises the 27 RBs, while the second downlink bandwidth forthe UE 1 comprises the 10 RBs allocated to the UE 1. Similarly, thesecond downlink bandwidth for the UE 2 comprises the 15 RBs allocated toit. The mapping information for the UE 1 comprises the “Offset 1=10”information and the mapping information for the UE 2 comprises the“Offset 2=3” information.

Thus, if the base station 28 transmits a message using RB 10—in a giventransmission time interval or instant—and that message includes aresource identifier pointing to RBs 12-14 using the first numberingscheme, the UE 1 would subtract Offset 1=10, to get RBs 2-4 in its ownnumbering scheme. Similarly, the UE 2 would subtract Offset 2=3 from12-14, and would get RBs 9-11 in its own numbering scheme. The “mappingfunction” used by each UE might thus be subtracting a UE-specific offsetfrom the RB numbers identified in the message, which may be a PhysicalDownlink Control Channel, PDCCH, transmission by the base station 28,for example.

In another embodiment, the modification might be the addition of theUE-specific offset to the RB numbers indicated by the base station 28.In both examples, a linear resource block numbering is assumed. Otherresource block numbering schemes such as positive and negative resourceblock numbers relative to a center frequency or a spiral resource blocknumbering starting in the center and spiraling outwards are otherpossible numbering schemes. The teachings herein are not limited to aspecific numbering scheme and it will be appreciated that the mappinginformation provided to a UE and the corresponding mapping function usedby the UE for translating base-station resource reference intoUE-specific resource references will depend on the resource referencingschemes in use.

Whereas base stations in LTE were referred to as eNBs, radio accessnodes in 5G systems may be referred to as “gNBs.” A gNB operatingaccording to an embodiment of the teachings herein provides mappinginformation to respective UEs, enabling each UE to translate theresource identifiers from the resource referencing scheme used by thegNB for the radio resource contained within a first bandwidth, intoUE-specific resource identifiers that are mapped into the resourcesubsets allocated to or associated with each UE. Of course, the gNB maytransmit UE-specific messages that contain resource identifiers that arealready expressed in terms of the UE-specific referencing scheme, whilesending resource identifiers in messages intended for receipt by morethan one UE that are expressed in terms of the gNB's referencing scheme.

In at least one embodiment herein, a gNB or other base station 28 usesdifferent message “sizes” when sending resource identifiers in a commonsearch space versus a device-specific (UE-specific) search space. Thatis, when sending a resource identifier in a message transmitted in acommon search space for receipt by more than one UE, the resourceidentifier is expressed in terms of the overall resource space—i.e., theresource space represented by the overall bandwidth at issue. However,when sending a resource identifier in a message transmitted in adevice-specific search space for receipt by a particular device, theresource identifier is expressed in terms of the allocated resourcespace—i.e., the resource space represented by the bandwidth allocationassociated with the device. Because the allocated bandwidth may be muchsmaller than the overall bandwidth, it takes fewer bits to uniquelyidentify resources—e.g., RBs—within the allocated bandwidth than isrequired for identifying those same resources within the overallbandwidth.

Complementing the different numbers of bits needed to identify resourcesin the overall bandwidth at issue versus the allocated bandwidthassociated with a given device 22, the devices 22 may be configured tohandle the different message sizes. For example, a UE searching for aPDCCH message in a common search space may assume a different resourceallocation field size than when it searches for a PDCCH message in aUE-specific search space. The UE may also assume a different DownlinkControl Information (DCI) size in this case. Also, note that it is notnecessary to define device-specific offsets in relation to an anchorequal to RB 0 (in base-station numbering). The anchor may be arbitraryand need not be known at the devices 22, as long as it is consistent forall devices 22 served by the base station 28 at issue. Different basestations 28 may have different anchors.

FIG. 10 illustrates an example embodiment or configuration where the BShas chosen RB 7 to be the anchor. This choice is reflected in that theOffset 1=3 and the Offset 2=−4. Thus, offsets may be negative. TheseUE-specific offsets are transmitted to the UEs, e.g., upon thesemi-static configuration of their bandwidth locations within the largerbandwidth.

FIG. 10 also illustrates the transmission of Downlink ControlInformation (DCI) by the BS, which identifies a data region of commoninterest to the UEs 1 and 2, and which identifies the involved RBs usingthe base-station resource referencing scheme. Notably, despiteexpressing the common data-region RBs in terms of its own resourcenumbering scheme, the base station does adjust for the fact that RB 7serves as the reference for the UE-specific offsets. Assuming that thecommon data-region RBs are numbered 12-14 in the base-station scheme,the resource identifier sent by the base station 28 in the common PDCCHidentifies RBs 5-7. The UE 1 subtracts Offset 1 (=3) to yield RBs 2-4within its own resource space, and the UE 2 subtracts Offset 2 (=−4)from 5-7 to obtain RBs 9-11 within its own resource space. Notably, asseen in conjunction with FIG. 7, both offsetting schemes result in theUEs 1 and 2 resolving the resource identifiers correctly, such that bothUEs 1 and 2 properly identify the RBs 12-14 (in absolute BS numbering)as being the common data-region RBs pointed to in the PDCCH message theyreceive from the BS in the common search space.

FIG. 10 demonstrates that a base station 28 can choose an arbitraryanchor point within the overall bandwidth of interest, and the choice istransparent to the devices 22 being served, as the base station 28 canadjust the value(s) of the resource identifiers it sends in commonmessages, in dependence on where the anchor or reference point for theUE-specific offsets is located within the overall bandwidth. By way ofexample, the anchor may be the location of BS RB 0 or RB N−1, or thecenter RB or the center frequency of the overall bandwidth or thelocation of a sync signal or synchronization signal block SSB or thePhysical Broadcast Channel (PBCH) or any other location. In at least oneembodiment, the base station 28 chooses the anchor to minimize thenumber of bits needed to encode the offsets.

The encoding of the offsets is also considered herein. The encodingresolution might be different from the single-RB resolution that thedevices 22 use. For example, rather than expressing offsets at the RBresolution, the offsets may be expressed more coarsely, such as inmultiples of RBs, rather than in single-RB increments. In an example,the device-specific offsets are expressed in terms of L times (somenumber of RBs), where L is an integer. Such an approach saves signalingbits but does force the base station 28 to use a coarser grid on whichto allocate devices 28.

Now consider a scenario where the network 20 reconfigures a device 22 toanother part of the overall bandwidth 14—i.e., where the allocatedbandwidth 18 of the device 22 is “moved” within the overall bandwidth atissue. Such changes may occur, for example, as a function of networkload or device mobility resulting in a change in serving base stationsfor the device 22. Changing the allocated bandwidth location changes thedevice-specific offset, which can more generally be stated as sayingthat the mapping function to be used by the device 22 for translatingfrom the base-station resource referencing scheme into thedevice-specific resource referencing scheme changes.

Hence, the offset or other mapping information used by the device 22must be updated to reflect the changed allocation location and suchinformation can be provided to the device 22 as a parameter in RRCreconfiguration or handover signaling. More generally, the device 22 isprovided with, or the device 22 derives, new mapping information asneeded.

FIG. 11 illustrates a further variation contemplated herein. In thisexample embodiment or instance, the offset that relates device-specificresource numbering to the base-station resource numbering is definedrelative to the allocated bandwidth of each device 22 being supported.The offset is relative to a reference that is preferably within a commonbandwidth of all devices 22 that should be capable of receiving a commonmessage from the base station 28.

In the diagram the reference is selected at the bottom of the commonbandwidth. However, other positions are possible as well. In theexample, the Offset 1=0 and the Offset 2=7. The base station 28references scheduled resources relative to the reference, although itdoes so using the numbering scheme associated with the overall bandwidth14. For example, to reference RBs 13-15 (in the BS coordinate system) ina common message sent to the UEs 1 and 2, the BS would signal 3-5. Whilestill expressed within the BS resource referencing scheme, theseresource identifier values are relative rather than absolute—i.e., theyare relative to the RB=10 anchor point within the overall bandwidth atissue.

Correspondingly, to properly map the resource identifier values from theBS scheme into the applicable device-specific scheme, the UE 1 addsOffset 1 (0) to them, which results in the UE 1 decoding data from RBs3-5 within its own referencing scheme. Of course, these values “point”to RBs 13-15 within the overall bandwidth 14, as is proper. Similarly,the UE 2 adds Offset 2 (7) to the values signaled by the BS, whichresults in the UE 2 decoding data from the correct RBs.

Notably, the reference does not necessarily have to be within the commonbandwidth and FIG. 12 illustrates an example of such an approach. Here,the Offset 1=−1 and the Offset 2=6. To address the same bandwidth asreferenced in the preceding example, the base station 28 signalsresource identifiers 4-6. The UE 1 adds Offset 1 (−1) to the signaledvalues and uses resources 3-5 in its local referencing or coordinatesystem. The UE 2 adds Offset 2 (6) to the signaled values and useresources 10-12 in its local coordinate system. If the offset referenceis outside the common bandwidth, a potentially larger field is neededfor the resource allocation assignment. For example, in FIG. 11, onlythree bits were needed, while in FIG. 12 4 bits are needed.

One advantage of the approach seen in FIG. 11 is that signaling in thecommon search space only requires as many bits as are needed to addressthe common bandwidth while the approach seen in FIG. 10 requires theresource allocation field to accommodate the number of bits needed foridentifying resources within the overall bandwidth at issue. Of course,the approach illustrated in FIG. 11 requires a reconfiguration of theUE-specific offsets if the common bandwidth changes, e.g. due tobandwidth allocation change of a single UE. Alternatively, the referencemay be kept constant but in this case the resource allocation field sizemay increase.

Among other advantages, the teachings herein allow for full flexibilityof per-device bandwidths while enabling the smallest possible payloadfor signaling device-specific RB allocations and while allowing fornon-ambiguous signaling of common-space RB allocations. In an exampleimplementation, a device 22 is configured with a bandwidth allocation(also referred to as a frequency allocation) that occupies a portion ofthe bandwidth (frequency range) that a serving base station 28 uses toserve any number of devices 22.

The device 22 is configured to receive a device-specific offset, and toreceive a downlink control message in a common search space. The messageincludes a resource identifier, e.g., a data region location indicator(resource block assignment), and the device 22 is configured to identifya set of resource blocks based on the data region location indicator andthe device-specific offset. Further, the device 22 is configured toreceive a data codeword in the data region in the identified set ofresource blocks—that is, the device 22 is configured to decode the datacodeword from the correctly-identified radio resources.

The device 22 uses different formulas—mapping functions—to calculate theresource block(s) to be used for reception or transmission dependingwhether the involved DCI has been received in a common search space usedby multiple devices 22, or a device-specific search space that isspecific to the device 22. The serving base station 28 may use differentresource block field sizes (and thus potentially also different DCIsizes) for DCI in common search spaces versus DCI in the UE-specificsearch space, and a device 22 in such embodiments is configured tocorrectly receive (process) the differently-sized resource block fieldsand/or DCI.

Notably, modifications and other embodiments of the disclosedinvention(s) will come to mind to one skilled in the art having thebenefit of the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that theinvention(s) is/are not to be limited to the specific embodimentsdisclosed and that modifications and other embodiments are intended tobe included within the scope of this disclosure. Although specific termsmay be employed herein, they are used in a generic and descriptive senseonly and not for purposes of limitation.

What is claimed is:
 1. A method of operation by a wireless communicationdevice with respect to a wireless communication network, the methodcomprising: receiving a resource identifier from a network node in thewireless communication network, the resource identifier indicating avalue that maps directly to numbered radio resources within a definedportion of radio frequency spectrum, if the resource identifier is notreceived in a common search space, and maps indirectly to the numberedradio resources according to an offset, if the resource identifier isreceived in a common search space; and transmitting or receiving on thenumbered radio resources.
 2. The method of claim 1, wherein theindicated value is a starting number and wherein, if the resourceidentifier was not received in a common search space, the numbered radioresources are identified by interpreting the starting number asindicating a starting physical resource block within a set of physicalresource blocks that are numbered according to a numbering schemereferenced to the defined portion of radio spectrum.
 3. The method ofclaim 2, wherein, if the resource identifier was received in a commonsearch space, the numbered radio resources are identified byinterpreting the starting number plus the offset, as indicating thestarting physical resource block.
 4. The method of claim 1, wherein thedefined portion of radio spectrum spans a subset of physical resourceblocks within an overall set of physical resource blocks spanned by anoverall bandwidth, and wherein the numbered radio resources are includedin the subset of physical resource blocks.
 5. The method of claim 1,wherein the numbered radio resources include a starting numbered radioresource, and wherein the starting numbered radio resource is determinedfrom the indicated value without the offset, if the resource identifierwas not received in a common search space, and wherein the startingnumbered radio resource is determined from the indicated value plus theoffset, if the resource identifier was received in a common searchspace, and wherein remaining ones of the numbered radio resources areidentified according to mapping information received from the networknode.
 6. A wireless communication device comprising: communicationcircuitry configured for wireless communication in a wirelesscommunication network; and processing circuitry operatively associatedwith the communication circuitry and configured to: receive a resourceidentifier from a network node in the wireless communication network,the resource identifier indicating a value that maps directly tonumbered radio resources within a defined portion of radio frequencyspectrum, if the resource identifier is not received in a common searchspace, and maps indirectly to the numbered radio resources according toan offset, if the resource identifier is received within a common searchspace; and transmit or receive on the numbered radio resources.
 7. Thewireless communication device of claim 6, wherein the indicated value isa starting number and wherein, if the resource identifier was notreceived in a common search space, the numbered radio resources areidentified by interpreting the starting number as indicating a startingphysical resource block within a set of physical resource blocks thatare numbered according to a numbering scheme referenced to the definedportion of radio spectrum.
 8. The wireless communication device of claim7, wherein, if the resource identifier was received in a common searchspace, the numbered radio resources are identified by interpreting thestarting number plus the offset, as indicating the starting physicalresource block.
 9. The wireless communication device of claim 6, whereinthe defined portion of radio spectrum spans a subset of physicalresource blocks within an overall set of physical resource blocksspanned by an overall bandwidth, and wherein the numbered radioresources are physical resource blocks included in the subset.
 10. Thewireless communication device of claim 6, wherein the numbered radioresources include a starting numbered radio resource, and wherein thestarting numbered radio resource is determined from the indicated valuewithout the offset, if the resource identifier was not received in acommon search space, and wherein the starting numbered radio resource isdetermined from the indicated value plus the offset, if the resourceidentifier was received in a common search space, and wherein remainingones of the numbered radio resources are identified according to mappinginformation received from the network node.